home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970326-19970626
/
000338_news@newsmaster….columbia.edu _Sat Jun 21 08:23:16 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id IAA25103
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 21 Jun 1997 08:23:15 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id IAA28804
for kermit.misc@watsun; Sat, 21 Jun 1997 08:23:14 -0400 (EDT)
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!panix!news.mathworks.com!europa.clark.net!news-peer.sprintlink.net!news.sprintlink.net!Sprint!ix.netcom.com!bhuber
From: bhuber@netcom.com (Bud Huber)
Subject: Re: Problems using Kermit 95 with COM1 and COM3.
Message-ID: <bhuberEC4EGp.H1@netcom.com>
Organization: Netcom
References: <5odrb1$mrv@duke.telepac.pt> <5of0ll$eng$1@newsmaster.cc.columbia.edu>
Date: Sat, 21 Jun 1997 10:00:25 GMT
Lines: 51
Sender: bhuber@netcom.netcom.com
Xref: news.columbia.edu comp.protocols.kermit.misc:7201
In article <5of0ll$eng$1@newsmaster.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>In article <5odrb1$mrv@duke.telepac.pt>,
>Paul Vieira <cel@mail.telepac.pt> wrote:
>: I have a PC ( NT 4.0) with 3 serial ports (each one is connected to a
>: modem). I made 3 scripts (one for each port) in Kermit 95 to receive
>: files from the outside. The problem is that I can't run the scripts on
>: COM1 and COM3 at the same time, because one of the modems will not
>: work (initialize). I think the problem is related with the IRQ's
>: ( COM1 and COM3 use the same IRQ). How can I resolve this problem?
>:
>This is a canned reply to all queries regarding the use of MS-DOS Kermit
>on Windows 95 and NT, which are coming in at an ever-increasing rate:
>
>MS-DOS Kermit is not recommended or supported for Windows 95 or NT for the
>very good reason that it was not written for those platforms. It can not
>make network connections, it does not understand long file names, TAPI
>port/modem sharing, and in many cases it cannot find the serial ports or
>modems at all. It expects to have full control of your PC: memory, video
>adapter, interrupt controller, serial port, network adapter. This is not
>possible under Windows 95 and NT. If MS-DOS Kermit works at all in those
>environments, it is an accident, it is risky, and it is very likely to run
>in a degraded mode.
>
>Kermit 95 is the recommended and supported software for Windows 95 and NT.
>It is fully native, 32-bit, multithread, protected-mode, preemptive
>multitasking, using only Windows 32 APIs, and is a 32-bit Winsock client for
>completely straightforward network connections that coexist with your Web
>browser and all other network applications. It has built-in support for
>nearly 60 different modems; it emulates over 25 different terminals; it is
>not only a serial communications program but also a Telnet and Rlogin
>client, and supports XYZMODEM protocols as well as Kermit file transfer.
>
>More information about Kermit 95 at:
>
> http://www.columbia.edu/kermit/k95.html
>
>- Frank
But Frank,
The gentleman clearly indicated he was having problems with Kermit 95,
not Kermit for DOS.
Ciao,
Bud
--
-----
Bud Huber <bhuber@netcom.com>